* Fix asyncio event loop cleanup with SSO auth

Previously, when applications using SSO authentication exited, the
asyncio event loop was closed while background tasks were still
running, resulting in:
- ERROR: Task was destroyed but it is pending
- RuntimeError: Event loop is closed

This issue occurred specifically with SSO authentication flows that
use push notifications, but not with password-only authentication.

This fix ensures proper cleanup by:
1. Cancelling all pending tasks before stopping the event loop
2. Giving tasks time (0.3s) to handle CancelledError gracefully
3. Waiting for the event loop thread to finish before closing

This prevents "Task was destroyed but it is pending" errors when
shutting down applications that use SSO with push notifications.

* Revert "Fix asyncio event loop cleanup with SSO auth"

This reverts commit 8364e1c.

* Close login websocket after authentication

During SSO authentication flows, a push notification websocket
(LoginPushNotifications) is created to handle 2FA, device approval,
and SSO data key requests.

This websocket was never closed after successful login, causing
it to remain active until application shutdown. This resulted in
asyncio errors about pending tasks being destroyed.

Fix: Close login.push_notifications in _on_logged_in() immediately
after authentication completes and before any post-login setup.

verify-records and verify-shared-folder commands added

Bug fixes